Bi-directional linking of product build information

ABSTRACT

Software product build information is bi-directionally linked. At least a first build instance of the software product is built and the first build instance is published by a supplier build repository. Responsive to an entity who is not the supplier indicating a use of the first build instance in a client product, build information relating to the use of the first build instance in the client product is received. The build information relating to the use of the first build instance in the client product is published by the supplier build repository.

BACKGROUND

Arrangements described herein relate to managing product builds.

Software developers often build applications using existing componentsin lieu of programming entire applications from scratch. Subroutinelibraries, program generators, visual programming systems and databasesare examples of software technologies that have been developed tofacilitate application development.

There are a number of reasons why using existing software components isdesirable. For example, the use of existing software components reducesthe amount of time dedicated to writing program code. Moreover,developers can focus on high level integration of the softwarecomponents into an application without necessarily having expertise toprogram the components themselves. Also, existing software componentsoftentimes have been extensively tested, thus reducing the amount oftime necessary for testing and de-bugging of an application using thesoftware components.

BRIEF SUMMARY

One or more embodiments disclosed within this specification relate tobi-directionally linking software product build information.

A method of bi-directionally linking software product build informationcan include building, via a supplier side processor, at least a firstbuild instance of the software product and publishing the first buildinstance by a supplier build repository. The method also can include,responsive to an entity who is not the supplier indicating a use of thefirst build instance in a client product, receiving build informationrelating to the use of the first build instance in the client product.The method further can include publishing by the supplier buildrepository the build information relating to the use of the first buildinstance in the client product.

Another embodiment can include a system having a processor. Theprocessor can be configured to initiate executable operations. Theexecutable operations can include building, via a supplier sideprocessor, at least a first build instance of the software product andpublishing the first build instance by a supplier build repository. Theexecutable operations also can include, responsive to an entity who isnot the supplier indicating a use of the first build instance in aclient product, receiving build information relating to the use of thefirst build instance in the client product. The executable operationsfurther can include publishing by the supplier build repository thebuild information relating to the use of the first build instance in theclient product.

Another embodiment can include a computer program product forbi-directionally linking software product build information. Thecomputer program product can include a computer-readable storage mediumhaving stored thereon program code that, when executed, configures aprocessor to perform a method. The method can include building, via asupplier side processor, at least a first build instance of the softwareproduct and publishing the first build instance by a supplier buildrepository. The method also can include, responsive to an entity who isnot the supplier indicating a use of the first build instance in aclient product, receiving build information relating to the use of thefirst build instance in the client product. The method further caninclude publishing by the supplier build repository the buildinformation relating to the use of the first build instance in theclient product.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a system for bi-directionallylinking software product build information in accordance with oneembodiment disclosed within this specification.

FIG. 2 is a flow chart illustrating a method of bi-directionally linkingsoftware product build information in accordance with one embodimentdisclosed within this specification.

FIG. 3 is a processing system for bi-directionally linking softwareproduct build information in accordance with one embodiment disclosedwithin this specification.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer-readablemedium(s) having computer-readable program code embodied, e.g., stored,thereon.

Any combination of one or more computer-readable medium(s) may beutilized. The computer-readable medium may be a computer-readable signalmedium or a computer-readable storage medium. The phrase“computer-readable storage medium” means a non-transitory storagemedium. A computer-readable storage medium may be, for example, but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, or device, or any suitablecombination of the foregoing. More specific examples (a non-exhaustivelist) of the computer-readable storage medium would include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a hard disk drive (HDD), a solid state drive (SSD), arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), a digital versatiledisc (DVD), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer-readable storage medium may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

A computer-readable signal medium may include a propagated data signalwith computer-readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer-readable signal medium may be any computer-readable medium thatis not a computer-readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer-readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber, cable, RF, etc., or any suitable combination ofthe foregoing. Computer program code for carrying out operations foraspects of the present invention may be written in any combination ofone or more programming languages, including an object orientedprogramming language such as Java™, Smalltalk, C++ or the like andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer, or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer, other programmable data processing apparatus,or other devices create means for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable medium that can direct a computer, other programmabledata processing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

For purposes of simplicity and clarity of illustration, elements shownin the figures have not necessarily been drawn to scale. For example,the dimensions of some of the elements may be exaggerated relative toother elements for clarity. Further, where considered appropriate,reference numbers are repeated among the figures to indicatecorresponding, analogous, or like features.

Arrangements described herein relate to bi-directionally linkingsoftware product build information between a supplier that providesproduct builds and entities that use the product builds. Severaldefinitions that apply throughout this document will now be presented.

As used herein, the term “product build” means a process by which aproduct is built. For example, a “product build X” refers to a processof manipulating source code to produce a product “X.” Certain productbuild information is typically constant across a product build such asthe product name, product owner, website, etc. Other product buildinformation is not constant, however. For example, different buildinformation may be associated with different build streams or buildinstances.

As used herein, the term “build stream” means a specific version of aproduct. For example, a “Product build X” may contain multiple buildstreams such as “Build stream 1.0”, “Build stream 1.5” and “Build streamlatest.” Product build information constant across a build stream mayinclude the version number, release lead, and supplier builds andcomponents.

As used herein, the term “build instance” means a specific instance inwhich product “X” is produced from source code. Build instancestypically are identified by build identifiers. A build identifier can bea time stamp, but this is not a requirement. A build stream can containmultiple build instances. Each build instance has a unique (for at leastthe build stream) build identifier. Each build instance also can have anassociated result identifier (e.g., success or failure, green or red,etc.).

As used herein, the term “build engine” means software that implements aproduct build to build a product. For instance, a build engine mayimplement a “product build X” to produce a build instance of product“X.” The build engine also may implement the “product build X” toproduce other build instances of product “X” when the source code forproduct “X” is updated/changed.

As used herein, the term “build result” means components built for aparticular build instance and associated build information related tothe build instance. The associated build information can be metadata,though this need not be the case.

As used herein, the term “build repository” means a storage areaconfigured to store one or more build streams and/or build instances. Abuild repository also may be configured to store various product buildinformation, such as information described herein. In illustration, abuild repository can include a database that stores product buildinformation for a product, build streams of the product and/or buildinstances of the product. The database also can identify where buildcomponents are stored in the build repository.

As used herein, the term “publish” means to store and make accessible toone or more entities for use. For example a repository may receive abuild instance and/or build information, store the build instance and/orbuild information, and make the build instance and/or build informationaccessible to one or more entities that choose to access the buildinstance and/or build information.

FIG. 1 is a block diagram illustrating a system 100 for bi-directionallylinking software product build information in accordance with oneembodiment disclosed within this specification. The system can include asupplier build engine 110, a supplier build repository 115, a clientside build engine 120 and a client build repository 125.

In operation, the supplier build engine 110 can, via a processor,execute a product build to create a build instance 140 for a supplierproduct 130. For example, the supplier build engine 110 can execute theproduct build to generate a build result 135 for the supplier product130. The build result 135 can include the build instance 140 andcorresponding build information 145. Execution of the product build canbe initiated by the supplier who maintains the supplier product 130 forwhich the build instance 140 is created.

The supplier build engine 110 can communicate the build result 135 tothe supplier build repository 115 to be published by the supplier buildrepository 115. The supplier build repository 115 can include fileswhere the components of the build instance 140 are stored, and adatabase in which the build information 145 is stored. Additional buildinstances and build information for the product also can be published bythe supplier build repository 115. The build instance 140 can includecomponents of the supplier product 130 built for that build instance140. The build information 145 can identify information about thesupplier side build of the build instance 140, for example informationrelated to the product for which the build instance 140 is built,information related to the build stream for which the build instance 140is built, the components of the supplier product 130 used in the buildinstance 140, and any other information relevant to the supplier product130, the build stream, the build instance 140 and/or the supplier whobuilt, via the supplier build engine 110, the build instance 140.

An entity, for example a user, group or organization who is not asupplier of the product, or a user, group or organization who is thesupplier of the product, can access the build instance 140 to buildother products that include the build instance 140, or that includecomponents of the supplier product 130 included in the build instance140. For example, the entity can access the build instance 140 from thesupplier build repository 115. As noted, the supplier build repository115 also may contain other build instances. Rules can be configured andenforced so that the latest good build instance 140 of the product isavailable to be accessed, or the same build instance 140 presently inuse elsewhere is available to be accessed. The invention is not limitedin this regard, however, and rules can be configured and enforced toallow other build instances to be accessed.

In illustration, an entity can access the build instance 140 using auniform resource identifier (URI) (e.g., a uniform resource locator(URL)) or access the build instance 140 in any other suitable manner.The entity may access the desired build instance 140 directly from thesupplier build repository 115, or another repository where the buildinstance 140 may be stored. For example, a first entity may use aparticular build instance 140 for their product, and publish the buildresult for that product by another repository. Such build result for thefirst entity's own product can include the build instance 140 and atleast a portion of the build information 145 for the build instance 140.A second entity may access the build instance 140, and any correspondingbuild information 145, from the repository of the first entity or fromthe supplier build repository 115. By way of example, the build resultfor the first entity's own product can indicate where the build instance140 may be accessed.

In some instances, the entity, for example a user representing theentity, may be required to enter entity and/or user data to access thebuild instance 140. For example, the user can provide a uniqueidentifier, such as a user name, email address, or the like, a passwordor pass code, etc. The present arrangements are not limited in thisregard, however.

Regardless of how an entity accesses the particular build instance 140,when the entity accesses the build instance 140, the corresponding buildinformation 145 also may be provided to that entity. The client sidebuild engine 120 can, via a processor, execute a product build for aclient product 150 to generate a build result 160 for the client product150. Execution of the client side product build can be initiated by anentity who maintains a client product 150 for which a build instance 165is created. The build result 160 can include a build instance 165 of theclient product 150 and build information for the build instance 165. Theclient product 150, and hence the build instance 165, can include one ormore components of the build instance 140. For example, the number ofcomponents of the build instance 140 that are used in the build instance165 of the client product 150 can be less than the total number ofcomponents of the build instance 140, though this need not be the case.

The client side build engine 120 can communicate the build result 160 tothe client build repository 125 to be published by the client buildrepository 125. The client build repository 125 can include files wherethe components of the build instance 165 are stored, and a database inwhich the build information 170 is stored. Additional build instancesand build information for the client side product also can be publishedby the client build repository 125.

The build information 170 can identify information about the client sidebuild of the build instance 165, for example information related to theclient product 150 for which the build instance 165 is built,information related to the build stream for which the build instance 165is built, the components of the client product 150 used in the buildinstance 165 and any other information relevant to the client product150, the build stream and/or the build instance 165. Moreover, the buildinformation 170 can identify build information about the build instance140 used in the build instance 165. For example, the build information170 can identify the supplier of the build instance 140, the supplierproduct 130 for which the build instance 140 is generated, the streamfor which the build instance 140 is generated, components of the buildinstance 140 that are used in the build instance 165, components of thesupplier product 130 used in the build instance 140, and any otherinformation relevant to the supplier product 130, the build stream forthe supplier product 130 and/or the build instance 140. The buildinformation 170 can be communicated to the client build repository 125for publishing by the product build used by the client side build engine120, or communicated to the client build repository 125 for publishingby another module which identifies the components of the build instance140 used in the build instance 165.

Further, client side build engine 120 can communicate to the supplierbuild repository 115 additional build information 180 for the buildinstance 140. In another arrangement, the additional build information180 for the build instance 140 can be provided by a user accessing thebuild instance 140, such as a user who is to retrieve the build instance140 and provide the build instance 140 to the client side build engine120. For example, the user can be prompted to enter such information,and such information can be validated before the user is provided accessto the build instance 140. In other arrangements, a portion of theadditional build information 180 can be provided by the user and aportion of the additional build information 180 can be provided by theclient side build engine 120.

The supplier build repository 115 may add the additional buildinformation 180 to the existing build information 145, therebyassociating the additional build information 180 with the build instance140 and existing build information 145, and causing the additional buildinformation 180 to be published by nature of the build information 145being published. Because the additional build information 180 isprovided by the client side build engine 120, the additional buildinformation 180 indicates the entity's use of the build instance 140.

Such additional build information 180 can identify the entity that usesthe build instance 140 to generate the build instance 165, theparticular build instance 140, the particular build instance 165, thecomponents of the build instance 140 used in the build instance 165,components of the client product 150 used in the build instance 165, thebuild stream for which the build instance 165 is generated, the buildstream for which the build instance 140 is generated, the supplierproduct 130 for which the build instance 140 is generated, the clientproduct 150 for which the build instance 165 is generated and/or thelike. The additional build information 180 can be communicated to thesupplier build repository 115 for publishing by the product build usedby the client side build engine 120, or can be communicated to thesupplier build repository 115 for publishing by another module whichidentifies the components of the build instance 140 used in the buildinstance 165. Accordingly, the build information contained in, andpublished by, the supplier build repository 115 can identify clientproducts (such as the client product 150) which use particular buildinstances (such as the build instance 140) of the supplier product 130,as well as indicate dependencies and/or relationships.

At this point it should be noted that since the supplier buildrepository 115 and/or the client build repository 125 includeinformation which may be used to establish bi-directional linking ofbuild information related to the build instance 140, no additionalrepository and/or database is required to implement theprocesses/methods described herein.

Any of a variety of means can be used perform the aforementionedpublishing of the build results 135, 160. For example, using one or moresuitable file transfer (FTP) protocols, representational state transfer(REST) (e.g., in accordance with Open Services for LifecycleCollaboration Change Management (OSLC-CM)), or the like. Suitableapplication program interfaces (APIs) can be provided to facilitatepublishing of the build results in accordance with a suitable programprotocol, though this need not be the case. Further, the aforementioneddatabases can be updated with record updates or addition of new records,new information can be posted, or the like. When a series of buildinstances publish, it may only be necessary to update product buildand/or product stream information in the event of a change of theinformation. In some instances, only information for the most recentbuild instance 165 of a client product 150 need be kept.

The system 100 further can include a supplier repository manager 190.The supplier repository manager 190 can be configured to monitor, basedon the build information (e.g., the build information 145), informationrelating to the usage of build instances (e.g., the build instance 140)in client products (e.g., the client product 150). The supplierrepository manager 190 also can be configured to delete or archive buildinstances, and corresponding build information, for those buildinstances not being used in the most recent versions of client products150 or not being used at all. If no current client products 150 areusing a particular build instance, the supplier repository manager 190can be confident that deleting or archiving that build instance will notaffect the client products. For example, if the build information 145indicates that the client product 150 is using the build instance 140, anew build instance of the supplier product 130 is built, and the buildinformation for the new build instance for the supplier product 130indicates that a new build instance of the client product 150 is usingthe new build instance of the supplier product 130, then the supplierrepository manager 190 can delete and/or archive the build instance 140and the associated build information 145.

Moreover, the supplier repository manager 190 can be configured toproactively notify entities maintaining client products (e.g., an entitymaintaining the client product 150) changes to particular components ofthe supplier product 130 that have been, or are planned to be,implemented subsequent to the use of such components in the clientproducts. In illustration, if a new build instance of the supplierproduct 130 has been built, the supplier repository manager 190 canidentify such new build instance and notify the entity managing theclient product 150 that the new build instance is available. Similarly,if a new build instance of the supplier product 130 has been planned,information regarding the plan can be added to the supplier buildrepository 115. The supplier repository manager 190 can identify plan tobuild the new build instance and notify the entity managing the clientproduct 150 that the new build instance is planned.

The supplier repository manager 190 can communicate messages to suchentities to notify the entities of such changes, for example via email,text messaging, or the like. Further, if significant defects arediscovered in a particular build instance, the supplier repositorymanager 190 identify entities which have used the particular buildinstance, and notify communicate messages to such entities to notify theentities of the defects and/or recommend that such entities use anotherbuild instance in their respective client products 150.

In addition, by knowing which entities are using the supplier product130, the owner of the supplier product 130 (e.g., via the supplierrepository manager 190) is able to, based on the additional buildinformation 180 added to the build information 145, perform verificationas to whether the client products 150, or the entities that manage theclient products 150, are complying with license requirements pertainingto the use of the supplier product 130 (e.g., the build instance 140) inthe client product 150. In illustration, the additional buildinformation 180 can be processed by the supplier repository manager 190to determine whether the additional build information 180 includesinformation pertinent to a particular licensing scheme. Such informationcan be automatically requested of an entity when the entity requests toaccess a build instance.

The various notification/publications described herein can becommunicated in any suitable manner, for example via one or morecommunication networks. Such communication networks can be implementedas, or include, any of a variety of different networks such as a WAN, aLAN, a wireless network, a mobile network, a Virtual Private Network(VPN), the Internet, the Public Switched Telephone Network (PSTN), orthe like.

FIG. 2 is a flow chart illustrating a method of bi-directionally linkingsoftware product build information in accordance with one embodimentdisclosed within this specification. At step 202, via a client sideprocessor, at least a first build instance of the software product canbe build. At step 204, the first build instance can be published by asupplier build repository. At step 206, responsive to an entity who isnot the supplier indicating a use of the first build instance in aclient product, build information relating to the use of the first buildinstance in the client product can be received. At step 208, the buildinformation relating to the use of the first build instance in theclient product can be published by the supplier build repository.

FIG. 3 is a processing system 300 for bi-directionally linking softwareproduct build information in accordance with one embodiment disclosedwithin this specification. The processing system 300 can include atleast one processor 305 (e.g., a central processing unit) coupled tomemory elements 310 through a system bus 315 or other suitablecircuitry. As such, the processing system 300 can store program codewithin the memory elements 310. The processor 305 can execute theprogram code accessed from the memory elements 310 via the system bus315. It should be appreciated that the processing system 300 can beimplemented in the form of any system including a processor and memorythat is capable of performing the functions and/or operations describedwithin this specification. For example, the processing system 300 can beimplemented as a computer, or a plurality of computers which arecommunicatively linked, for example via one or more communicationnetworks.

The memory elements 310 can include one or more physical memory devicessuch as, for example, local memory 320 and one or more bulk storagedevices 325. Local memory 320 refers to RAM or other non-persistentmemory device(s) generally used during actual execution of the programcode. The bulk storage device(s) 325 can be implemented as a hard diskdrive (HDD), solid state drive (SSD), or other persistent data storagedevice. The processing system 300 also can include one or more cachememories (not shown) that provide temporary storage of at least someprogram code in order to reduce the number of times program code must beretrieved from the bulk storage device 325 during execution.

Input/output (I/O) devices such as one or more network adapters 330 canbe coupled to processing system 300 to enable processing system 300 tobecome coupled to other systems, computer systems, remote printers,and/or remote storage devices through intervening private or publicnetworks. Modems, cable modems, transceivers, and Ethernet cards areexamples of different types of network adapters 330 that can be usedwith processing system 300.

As pictured in FIG. 3, the memory elements 310 can store the componentsof the system 100 of FIG. 1, such as the supplier build engine 110, thesupplier build repository 115 and the supplier repository manager 190.Being implemented in the form of executable program code, thesecomponents of the system 100 can be executed by the processing system300 and, as such, can be considered part of the processing system 300.Moreover, the supplier build engine 110, the supplier build repository115 and the supplier repository manager 190 are functional datastructures that impart functionality when employed as part of theprocessing system of FIG. 3.

A processing system similar to that described for FIG. 3 can be used tohost the client side build engine 120 and/or the client build repository125 described in FIG. 1.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “includes,”“including,” “comprises,” and/or “comprising,” when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment disclosed within thisspecification. Thus, appearances of the phrases “in one embodiment,” “inan embodiment,” and similar language throughout this specification may,but do not necessarily, all refer to the same embodiment.

The term “plurality,” as used herein, is defined as two or more thantwo. The term “another,” as used herein, is defined as at least a secondor more. The term “coupled,” as used herein, is defined as connected,whether directly without any intervening elements or indirectly with oneor more intervening elements, unless otherwise indicated. Two elementsalso can be coupled mechanically, electrically, or communicativelylinked through a communication channel, pathway, network, or system. Theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill also be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms, as these terms are only used to distinguishone element from another unless stated otherwise or the contextindicates otherwise.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the embodiments disclosed within this specification havebeen presented for purposes of illustration and description, but are notintended to be exhaustive or limited to the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of theembodiments of the invention. The embodiments were chosen and describedin order to best explain the principles of the invention and thepractical application, and to enable others of ordinary skill in the artto understand the inventive arrangements for various embodiments withvarious modifications as are suited to the particular use contemplated.

What is claimed is:
 1. A method of bi-directionally linking softwareproduct build information, comprising: building, via a supplier sideprocessor, at least a first build instance of the software product;publishing the first build instance by a supplier build repository;responsive to an entity who is not the supplier indicating a use of thefirst build instance in a client product, receiving build informationrelating to the use of the first build instance in the client product;and publishing by the supplier build repository the build informationrelating to the use of the first build instance in the client product.2. The method of claim 1, wherein the build information relating to theuse of the first build instance in the client product indicatescomponents of the first build instance that are used in the clientproduct.
 3. The method of claim 2, wherein the number of components ofthe first build instance that are used in the client product are lessthan the total number of components of the first build instance.
 4. Themethod of claim 1, further comprising: building at least a second buildinstance of the software product; publishing the second build instanceto the supplier build repository; and responsive to the entityindicating a use of the second build instance in the client product,archiving the first build instance of the software product.
 5. Themethod of claim 1, further comprising: building at least a second buildinstance of the software product; publishing the second build instanceto the supplier build repository; and responsive to the entityindicating a use of the second build instance in the client product,deleting the first build instance of the software product.
 6. The methodof claim 1, further comprising: building at least a second buildinstance of the software product; publishing the second build instanceto the supplier build repository; and notifying the entity that thesecond build instance is available.
 7. The method of claim 1, furthercomprising: identifying a plan to build at least a second build instanceof the software product; and notifying the entity of the plan to buildthe second build instance of the software product.
 8. The method ofclaim 1, further comprising: determining, based on the build informationrelating to the use of the first build instance in the client product,whether the entity is complying with at least one license requirementpertaining to the use of the first build instance in the client product.9. A system comprising: a processor programmed to initiate executableoperations comprising: building, via a supplier side processor, at leasta first build instance of the software product; publishing the firstbuild instance by a supplier build repository; responsive to an entitywho is not the supplier indicating a use of the first build instance ina client product, receiving build information relating to the use of thefirst build instance in the client product; and publishing by thesupplier build repository the build information relating to the use ofthe first build instance in the client product.
 10. The system of claim9, wherein the build information relating to the use of the first buildinstance in the client product indicates components of the first buildinstance that are used in the client product.
 11. The system of claim10, wherein the number of components of the first build instance thatare used in the client product are less than the total number ofcomponents of the first build instance.
 12. The system of claim 9, theexecutable operations further comprising: building at least a secondbuild instance of the software product; publishing the second buildinstance to the supplier build repository; and responsive to the entityindicating a use of the second build instance in the client product,archiving the first build instance of the software product.
 13. Thesystem of claim 9, the executable operations further comprising:building at least a second build instance of the software product;publishing the second build instance to the supplier build repository;and responsive to the entity indicating a use of the second buildinstance in the client product, deleting the first build instance of thesoftware product.
 14. The system of claim 9, the executable operationsfurther comprising: building at least a second build instance of thesoftware product; publishing the second build instance to the supplierbuild repository; and notifying the entity that the second buildinstance is available.
 15. The system of claim 9, the executableoperations further comprising: identifying a plan to build at least asecond build instance of the software product; and notifying the entityof the plan to build the second build instance of the software product.16. The system of claim 9, the executable operations further comprising:determining, based on the build information relating to the use of thefirst build instance in the client product, whether the entity iscomplying with at least one license requirement pertaining to the use ofthe first build instance in the client product.
 17. A computer programproduct for bi-directionally linking software product build information,the computer program product comprising a computer readable storagemedium having program code stored thereon, the program code executableby a processor to perform a method comprising: building, by a supplierside processor, at least a first build instance of the software product;publishing, by the processor, the first build instance by a supplierbuild repository; responsive to an entity who is not the supplierindicating a use of the first build instance in a client product, by theprocessor, receiving build information relating to the use of the firstbuild instance in the client product; and by the processor, publishingby the supplier build repository the build information relating to theuse of the first build instance in the client product.
 18. The computerprogram product of claim 17, wherein the build information relating tothe use of the first build instance in the client product indicatescomponents of the first build instance that are used in the clientproduct.
 19. The computer program product of claim 18, wherein thenumber of components of the first build instance that are used in theclient product are less than the total number of components of the firstbuild instance.
 20. The computer program product of claim 17, the methodfurther comprising: building, via the processor, at least a second buildinstance of the software product; publishing, via the processor, thesecond build instance to the supplier build repository; and responsiveto the entity indicating a use of the second build instance in theclient product, deleting or archiving, via the processor, the firstbuild instance of the software product.